Hey @markhallen I know you were not there yesterday but we discussed and agreed that bun will be implemented as it's own ecosystem independent of npm & yarn.

Hi @markhallen,

I noticed some differences in the structures of your Bun PRs. I thought it might follow a structure similar to the one used in the Docker Compose PR.

For example, it could look like this if we follow the same approach:

  - lib/dependabot
    - common (or shared)
    - npm_and_yarn
        - file_fetcher
           ...
        - file_parser
          ....
       - file_updater
         ...
       - file_fetcher.rb
       - file_parser.rb
       - file_updater.rb
       ... so on
    - npm_and_yarn.rb
    - bun
         - file_fetcher
           ...
        - file_parser
          ....
       - file_updater
         ...
       - file_fetcher.rb
       - file_parser.rb
       - file_updater.rb
       ... so on
    - bun.rb```

If you follow this structure, you won’t need to make any changes to npm_and_yarn. Later, when we separate other package managers, we can adopt the same structure to create individual npm, pnpm, and yarn folders. This will allow us to treat them as distinct ecosystems while retaining npm_and_yarn for compatibility and managing deprecation/unsupported lifecycles.

Thanks @kbukum1

As discussed on Friday. This PR was put together before the change in approach. It was decided in the Friday standup that we proceed with these PR's as-is. We will then follow-up with a PR migrating to the new structure which will have the structure you have outlined above. This PR will then serve as an example for the migration of the other Javascript ecosystems.